-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SM-1097] Add support for manpage generation #175
Conversation
I think we should switch to generating manpages in the CI and possibly have them be a release artifact? Realistically they are only going to be used if we start distributing linux packages for the CLI. |
a4aa3b5
to
20c28e3
Compare
No New Or Fixed Issues Found |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #175 +/- ##
==========================================
+ Coverage 60.66% 60.67% +0.01%
==========================================
Files 173 174 +1
Lines 10628 10631 +3
==========================================
+ Hits 6447 6450 +3
Misses 4181 4181 ☔ View full report in Codecov by Sentry. |
# Conflicts: # crates/bws/src/config.rs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dani-garcia approved above, thanks for this! Something I just thought of...
One potential thing to add if you were open to it- adding the instructions you have in this PR for the compile time man pages to crates/bws/README.md
?
# Conflicts: # crates/bws/Cargo.toml # crates/bws/src/main.rs # crates/bws/src/render.rs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The manpage support and pipeline changes look good! 👍🏻
Type of change
Objective
Implement support for generating manpages at compile-time. Extracted from PR #103. The manpages also get generated in CI and uploaded as artifacts.
Note that because the CLI struct needs to be accessed by a build script, it had to be extracted to a separate self contained file.
How to generate manpages locally
The manpages get generated by a build script, and are available in the crate's build script OUT_DIR, to get it:
The output path is going to be something like
sdk/target/debug/build/bws-4acb75a675879df1/out
.Copy them to a better location, and then you can view the pages:
man ./my-pages/bws.1
man ./my-pages/bws-project.1
man ./my-pages/bws-secret.1
If you install them in a system path, you could also just access them with
man bws
, but that path is system specific. In Ubuntu I think it is/usr/share/man
Screenshots